Greptile Summary

This PR addresses a Docker container environment isolation issue that prevented the Copilot functionality from working in containerized deployments. The fix adds two environment variables (COPILOT_API_KEY and SIM_AGENT_API_URL) to all three Docker Compose configurations (docker-compose.local.yml, docker-compose.prod.yml, and docker-compose.ollama.yml).

The root cause was that Docker containers run in isolated environments and don't automatically inherit environment variables from the host system's .env file. Even when users correctly set COPILOT_API_KEY=sk-sim-copilot-xxxx in their .env file, the simstudio service running inside the Docker container couldn't access this variable, resulting in "Unauthorized request" errors in the Copilot panel.

The solution follows Docker Compose's standard pattern for environment variable propagation using ${VARIABLE_NAME} syntax. This allows Docker Compose to read values from the host environment (including .env files) and pass them into the containers at runtime. The changes are applied consistently across all deployment scenarios (local development, production, and Ollama-based setups) to ensure uniform behavior.

This fix integrates seamlessly with the existing codebase's Docker infrastructure, following the same patterns used for other environment variables like DATABASE_URL, BETTER_AUTH_SECRET, and ENCRYPTION_KEY that are already properly configured in these compose files.

Confidence score: 5/5

• This PR is safe to merge with minimal risk as it only adds environment variable mappings without changing application logic
• Score reflects the straightforward nature of the fix and consistent application across all Docker Compose files
• No files require special attention as the changes follow established patterns and are identical across all three compose files

_{3 files reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}